Task: Implementation Governance

This chapter provides an architectural oversight of the implementation.

Purpose

The objectives of Phase G are:

To formulate recommendations for each implementation project
To govern and manage an Architecture Contract covering the overall implementation and deployment process
To perform appropriate governance functions while the solution is being implemented and deployed
To ensure conformance with the defined architecture by implementation projects and other projects
To ensure that the program of solutions is deployed successfully, as a planned program of work
To ensure conformance of the deployed solution with the Target Architecture
To mobilize supporting operations that will underpin the future working lifetime of the deployed solution

Relationships

Inputs	Mandatory: Architecture Contract Architecture Definition Document Architecture Repository Architecture Requirements Specification Architecture Roadmap Architecture Vision Capability Assessment Change Request Implementation and Migration Plan Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Statement of Architecture Work Tailored Architecture Framework Transition Architecture	Optional: None
Outputs	Architecture Contract Change Request Compliance Assessment Solution Building Blocks

Main Description

Figure: Phase G: Implementation Governance

Approach

It is here that all the information for successful management of the various implementation projects is brought together. Note that, in parallel with Phase G, there is the execution of an organizational-specific development process, where the actual development happens.

To enable early realization of business value and benefits, and to minimize the risk in the transformation and migration program, the favored approach is to deploy the Target Architecture as a series of transitions. Each transition represents an incremental step towards the target, and each delivers business benefit in its own right. Therefore, the overall approach in Phase G is to:

Establish an implementation program that will enable the delivery of the Transition Architectures agreed for implementation during the Migration Planning phase
Adopt a phased deployment schedule that reflects the business priorities embodied in the Architecture Roadmap
Follow the organization's standard for corporate, IT, and architecture governance
Use the organization's established portfolio/program management approach, where this exists
Define an operations framework to ensure the effective long life of the deployed solution

Phase G establishes the connection between architecture and implementation organization, through the Architecture Contract.

Project details are developed, including:

Name, description, and objectives
Scope, deliverables, and constraints
Measures of effectiveness
Acceptance criteria
Risks and issues

Implementation governance is closely allied to overall architecture governance, which is discussed in Part VII, Architecture Governance .

A key aspect of Phase G is ensuring compliance with the defined architecture(s), not only by the implementation projects, but also by other ongoing projects within the enterprise. The considerations involved with this are explained in detail in Part VII, Architecture Compliance .

Steps

Confirm Scope and Priorities for Deployment with Development Management

Review migration planning outputs and produce recommendations on deployment
Identify enterprise architecture priorities for development teams
Identify deployment issues and make recommendations
Identify building blocks for replacement, update, etc.
Perform gap analysis on enterprise architecture and solutions framework
The gaps in the existing enterprise solutions framework need to be identified and the specific Solution Building Blocks (SBBs) required to fill these gaps will be the identified by the solutions architects. These SBBs may have a one-to-one or many-to-one relationship with the projects. The solutions architects need to define exactly how this will be done. There may be other projects working on these same capabilities and the solutions architects need to ensure that they can leverage best value from these investments.
Produce a gap analysis report

Identify Deployment Resources and Skills

The project resources will include the development resources which will need to be educated in the overall enterprise architecture deliverables and expectations from the specific development and implementation projects.

The following considerations should be addressed in this step:

Identify system development methods required for solutions development

Note:

There are a range of systems development methods and tools available to the project teams. The method should ideally be able to interoperate with the architecture outputs; for example, generate code from architecture artifacts delivered to date. This could be achieved through the use of modeling languages used for the enterprise architecture development that may be captured as inputs to the systems development tools and thereby reduce the cost of solutions development.
Ensure that the systems development method enables feedback to the architecture team on designs

Guide Development of Solutions Deployment

Formulate project recommendation
For each separate implementation and deployment project, do the following:
- Document scope of individual project in impact analysis
- Document strategic requirements (from the architectural perspective) in impact analysis
- Document change requests (such as support for a standard interface) in impact analysis
- Document rules for conformance in impact analysis
- Document timeline requirements from roadmap in impact analysis
Document Architecture Contract
- Obtain signature from all developing organizations and sponsoring organization
Update Enterprise Continuum directory and repository for solutions
Guide development of business & IT operating models for services
Provide service requirements derived from enterprise architecture
Guide definition of business & IT operational requirements
Carry out gap analysis between the Solution Architecture and operations
Produce Implementation Plan

Perform Enterprise Architecture Compliance Reviews

Review ongoing implementation governance and architecture compliance for each building block
Conduct post-development reviews
Close development part of deployment projects

Implement Business and IT Operations

Carry out the deployment projects including: IT services delivery implementation; business services delivery implementation; skills development & training implementation; communications documentation publication
Publish new Baseline Architectures to the Architecture Repository and update other impacted repositories, such as operational configuration management stores

Perform Post-Implementation Review and Close the Implementation

Conduct post-implementation reviews
Publish reviews and close projects

Closure on Phase G will be when the solutions are fully deployed once.

More Information

Supporting Materials	Original TOGAF 9 Text for Phase G: Implementation Governance

The Open Group gratefully acknowledge Capgemini for the creation of the Eclipse Process Framework Method Plugin for TOGAF9.

Downloads of the TOGAF documentation, are available under license from the TOGAF information web site. The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A book is also available (in hardcopy and pdf) from The Open Group Bookstore as document G091.